Closes #180

Summary

Adds ES/TS package specifier resolution so that import { foo } from '@myorg/storage-utils' produces real IMPORTS edges. Previously, fqn_module() treated npm package specifiers as file paths, producing QNs that matched no graph nodes — result: zero IMPORTS edges for all package imports.

How it works

1. Package map build (new Phase 1.5 in pipeline_run()): Walks the repo for package.json files, parses name + entry point (exports["."] → main → src/index.ts fallback). Builds a CBMHashTable mapping package names to resolved module QNs.

2. cbm_pipeline_resolve_module(ctx, module_path): New wrapper called instead of fqn_module() at IMPORTS-edge creation sites. If the specifier is a package reference and found in the map, returns the mapped QN. Handles subpath imports (@myorg/pkg/utils) by resolving relative to the package directory. Falls through to fqn_module() for relative paths and unknown packages.

3. Zero behavior change for non-JS repos: When no package.json files exist, pkg_map is NULL and all resolution falls through to fqn_module(). 0ms overhead.

Changes

• src/pipeline/pass_pkgmap.c (new) — package map build, free, and resolve functions
• src/pipeline/pipeline_internal.h — pkg_map field on ctx, cbm_pkg_entry_t struct, prototypes
• src/pipeline/pipeline.c — Phase 1.5 build step, ctx initialization, cleanup
• src/pipeline/pass_definitions.c:297 — resolve_module() instead of fqn_module()
• src/pipeline/pass_calls.c:91 — same
• src/pipeline/pass_usages.c:96 — same
• src/pipeline/pass_semantic.c:81 — same
• src/pipeline/pass_parallel.c:647 — same (in cbm_build_registry_from_cache)
• Makefile.cbm — added pass_pkgmap.c and test_pkgmap.c
• tests/test_pkgmap.c (new) — 20 unit tests

Test results

Build: Compiles cleanly on macOS (Apple Clang, arm64) with -Wall -Wextra -Werror

Test suite: 2761 passed, 0 failed (was 2741 — 20 new pkgmap tests)

Behavioral verification (monorepo matching issue scenario):

Created pnpm-like monorepo:

packages/storage-utils/package.json   {"name": "@myorg/storage-utils", "main": "src/index.ts"}
packages/storage-utils/src/index.ts   (exports validateDatasetName, buildSelectQuery)
apps/server/src/index.ts              (import { validateDatasetName } from '@myorg/storage-utils')

Edge cases tested (unit tests):

Scope boundary (not addressed)

• Relative import resolution (./utils) — already works
• tsconfig paths (@/components) — separate issue
• Barrel re-export resolution — separate enhancement
• External npm deps (in node_modules/) — outside project graph by design

Generated with agent-team via /issue